[release-4.20] CORENET-6378: back-port IP & MAC conflict detection e2e tests #30414
Conversation
Validates that KubeVirt VMs with preconfigured MAC and IP addresses maintain those addresses correctly before and after a vmi with duplicate IP/MAC request is made, and that the vmi with the duplicate address get the appropriate address conflict error event. Co-authored-by: Miguel Duarte Barroso <[email protected]> Signed-off-by: Ram Lavi <[email protected]> (cherry picked from commit 6dd2a93)
The requested IPs for the primary UDN attachment are not in the VMI spec, but in an annotation in the VMI. Hence, we need to fetch that particular annotation, and set it in the duplicate VMI. This was implemented using the builder pattern, since I suspect in the future we will need to further customize the VMI spec / metadata; this will make it simpler to extend the framework in the future. Signed-off-by: Miguel Duarte Barroso <[email protected]> (cherry picked from commit 13fdf10)
This way we can ensure appropriate cases are caught in a generic way. With it, we can safely expect to find IP conflicts when there are duplicate IPs in the network. In future commits, we will be able to catch MAC conflicts when there are duplicate MACs in the network Co-authored-by: Ram Lavi <[email protected]> Signed-off-by: Miguel Duarte Barroso <[email protected]> (cherry picked from commit fdb0584)
Verify KubeVirt VMs with preconfigured MAC address retain a requested MAC address before and after another VM is created requesting the same MAC address. And verify the other VM requesting the same MAC address get the appropriate address conflict error event. Signed-off-by: Or Mergi <[email protected]> (cherry picked from commit 0c58f2a)
openshift-ci-robot
added
the
jira/valid-reference
|
@ormergi: This pull request references CORENET-6378 which is a valid jira issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
@ormergi: The following tests failed, say
Full PR test history. Your PR dashboard. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/testwith openshift/origin/main/e2e-metal-ipi-ovn-bgp-virt-dualstack-techpreview openshift/ovn-kubernetes#2827 #30415 |
|
@ormergi, |
|
/testwith openshift/origin/main/periodic-ci-openshift-ovn-kubernetes-release-4.20-periodics-e2e-metal-ipi-ovn-bgp-virt-dualstack openshift/ovn-kubernetes#2827 #30415 |
|
@ormergi, |
|
/testwith openshift/origin/release-4.20/e2e-metal-ipi-ovn-bgp-virt-dualstack openshift/ovn-kubernetes#2827 #30415 |
|
Testing this PR with the incoming IP & MAC conflict bits and the [missing fix in tests] (#30415) on on 4.20 is green |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: maiqueb, ormergi The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
4 participants
This is manual check-pick of IP conflict detection tests [1] (commits 1-3) and MAC conflict detection tests [2] (commit 4).
Commits were cherry-picked from release-4.21 branch.
[1] #30197
[2] #30314